cmake: option MZ_PBKDF2: export mz_crypt_pbkdf2#1011
Conversation
ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughThis PR introduces a new CMake build option ChangesPBKDF2 Build Option Wiring
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
11816eb to
7c9bdaf
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 2befbca7-4f07-4682-8248-6a3285714724
📒 Files selected for processing (2)
mz_crypt.ctest/test_crypt.cc
💤 Files with no reviewable changes (1)
- test/test_crypt.cc
Let users use the function if they implement `mz_crypt_hmac_*` API without using CommonCrypto or OpenSSL.
7c9bdaf to
6920763
Compare
0dd25e0 to
6920763
Compare
|
@coderabbitai Please update your "Walkthrough" comment, |
|
✅ Action performedSummary regeneration triggered. |
| } | ||
|
|
||
| #if defined(HAVE_WZAES) | ||
| #if defined(HAVE_PBKDF2) |
There was a problem hiding this comment.
Let's remove all CMake changes. Then do #if !define(NO_PBKDF2).
Then in our CMake, let's use set_target_properties on minizip-ng to set -D NO_PBKDF2.
I don't think this is worthy of a feature flag.
There was a problem hiding this comment.
I guess you have meant a macro and a condition like this:
// Don't remove the right hand of the condition. Client apps may use the guarded function.
#if defined(HAVE_WZAES) || defined(HAVE_PBKDF2)
|
I can |
Let users use the function if they implement
mz_crypt_hmac_*API without using CommonCrypto or OpenSSL.